Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.04%. Comparing base (ccc9a1d) to head (5b68a25).

@@           Coverage Diff           @@
##             main      #47   +/-   ##
=======================================
  Coverage   93.04%   93.04%           
=======================================
  Files          16       16           
  Lines         503      503           
  Branches       18       18           
=======================================
  Hits          468      468           
  Misses         24       24           
  Partials       11       11           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

This is a Claude-generated comment. Brian's prompt: "reviewing #47, worried about contrast for a11y"

I ran the new autumn palette through WCAG 2.x contrast math against #FFFFFF and cross-checked against the upstream Paragon release-23.x token defaults to see which pairings actually matter in practice.

The headline result: only one token is a real concern — brand-base.

I initially flagged warning-base (#D4A537, 2.28 : 1) and the two accent tokens (#E8A33D / #5A8042) for failing against white text — but that's a non-issue. Upstream Paragon ships warning as #FFD900 (1.37 : 1 vs white), accent.a as #00BBF9 (2.22 : 1), and accent.b as #FFEE88 (~1.20 : 1). Those tokens by convention aren't paired with white text — .btn-warning uses dark text, and accents are decorative tints — so the autumn versions follow the same pattern and don't regress anything.

The real issue: brand-base at 4.40 : 1

Paragon's .btn-brand puts white labels on brand-500, so this is the most-exposed text-on-background pairing in the whole token system. Upstream's magenta clears AAA at 8.14 : 1; the new burnt-orange misses AA normal text (4.5 needed) by 0.1, and axe/Lighthouse will catch it the moment anyone themes an MFE with this. Darkening slightly — e.g. #B4501F (~4.9 : 1) or #A84A1C (~5.5 : 1) — keeps the burnt-pumpkin character and clears AA.

Token-structure notes

The structure looks fine — uses the token-reference + modify pattern Style Dictionary expects, and dist/light.css resolves cleanly. The one nit: the original had "$type": "color" at the file root; this PR moves it inside color. Both work, but worth a glance at the generated output to confirm parity.

Suggestion

Since this file is a teaching example, either works:

• Option A (recommended): nudge brand-base ~10% darker so the example ships AA-clean by default — consumers will copy this verbatim.
• Option B: keep the palette as-is and add a README note that real brand packages should run colors through a contrast checker, calling out brand-base specifically. Arguably more instructive.

Either way, this is a solid demo of token customization — the issue is just the specific orange.

I think it's worth doing both of those things, we should be compliant in our example but also provide pointers to how others can keep their themes accessible. I think we should update the contrast in this PR but we can make a follow-up PR for the README update if that's easier.